Known bugs and misbehaviour in Project Analyzer 2.9.x beta

Please let me know of any bugs you find.

- May produce OUT OF MEMORY or SUBSCRIPT OUT OF RANGE during analysis
  *** PLEASE LET ME KNOW IF YOU EXPERIENCE THESE ERRORS ***

- If you find a procedure, variable or constand marked "dead" even
  if it's not, please send me a piece of your source code (the
  declaration and the reference).

Features not implemented (at least for now):
- Cannot save analysis to an .ANL file, nor load

Most of the analysis is done correctly, but there is some
misbehaviour (minor problems, I hope):
- Doesn't understand compiler directives (#if xyz then)
- Constant references in the (declarations) section are not interpreted. 
  This may cause the following code to show a WM_USER as a 'dead' const:
  Global Const WM_USER = xyz
  Global Const WM_HELLO = WM_USER + 1
- May not always see the difference between two public variables that
  have the same name (as Public Form1.Var1 and Public Form2.Var1)
- ReDim MyTable(N) is interpreted as a new local table
- The size of variable and constant names is restricted to 40
  characters. Longer names are truncated.
- Doesn't understand the line continuation character '_' in VB 4.0
- The obsolete loop construction While..Wend is not counted in Nested loops

There are a few deficiencies in the FRX view (it works OK for most cases)
  * FRX view shows only graphical data.
    Textual data (like the List property of a ListBox) is not shown.
  * FRX view may label picture types strangely, like showing (Icon)
    when it isn't
  * FRX view doesn't understand if one control has more than 1 picture
    => Shows only one picture
  * FRX view doesn't understand other properties than
    .Picture, .Icon and .MouseIcon
  * FRX view can't handle SSCommand.Picture. Seems to me these pictures
    are stored differently